Runtime: extract a Runtime subdirectory for SPM #9063
Conversation
compnerd
force-pushed
the
runtime
branch
2 times, most recently
from
f3a5555 to
5cb3585
Compare
|
Can you elaborate on some of the higher level goals behind this change? |
|
@jakepetroules sure - the higher level goal here is to get to the point where we can build the Swift toolchain on Windows with the bootstrap compiler. With the new experimental SDK, we have Win32 SxS runtimes available and I would like to embed the runtime into the compiler itself. allowing the toolchain to run against the runtime that it was built against while uniformly building all the tools against the same runtime and the same compiler. Currently, the SPM Manifest runtime is built with the just built compiler and runtime as we build the vast majority of the toolchain with the just built compiler and runtime and rely on luck to build the swift frontend with the bootstrap compiler and runtime and then run against the new runtime (without ABI stability). This restructuring (it is mostly a move of 3 of the modules) allows us to create a separate subproject that will build only |
compnerd
requested review from
jakepetroules,
dschaefer2,
shawnhyam,
bripeticca,
plemarquand,
owenv,
bkhouri,
cmcgee1024 and
daveyc123
as code owners
|
@swift-ci please smoke test |
|
@swift-ci please test |
|
@swift-ci please smoke test Linux platform |
|
Please test with following PRs: @swift-ci please smoke test |
compnerd
force-pushed
the
runtime
branch
3 times, most recently
from
714a90e to
b757253
Compare
|
Please test with following PRs: @swift-ci please smoke test |
|
Can this be done without the large number of moves? |
|
Please test with following PRs: @swift-ci please smoke test |
No, that cannot be done. The large number of moves is due to the DocC bundles being checked in. We could remove the DocC bundles potentially. But we do need to have a new directory in between to allow building as a separate project, so the remaining moves (which are pretty small) need to be done. |
|
@swift-ci please test macOS platform |
1 similar comment
|
@swift-ci please test macOS platform |
|
@swift-ci please test macOS platform |
|
@swift-ci please test Linux platform |
|
@swift-ci please test Linux platform |
|
@swift-ci please test macOS platform |
|
Please test with following PRs: @swift-ci please test Windows platform |
|
Please test with following PRs: @swift-ci please test |
|
Please test with following PRs: @swift-ci please test Linux platform |
1 similar comment
|
Please test with following PRs: @swift-ci please test Linux platform |
Re-organise the "runtime" components (i.e. the Package Manifest runtime) into a separate directory. Introduce a separate CMake project for the build of this runtime to allow building the SPM tool with one version of the Swift runtime and the SPM Manifest Runtime witih a separate Swift runtime.
|
Please test with following PRs: @swift-ci please test Linux platform |
|
Please test with following PRs: @swift-ci please test Windows platform |
|
Please test with following PRs: @swift-ci please test macOS platform |
|
Please test with following PRs: @swift-ci please test macOS platform |
|
Please test with following PRs: @swift-ci please test macOS platform |
|
Please test with following PRs: @swift-ci please test macOS platform |
|
Please test with following PRs: @swift-ci please test |
|
Please test with following PRs: @swift-ci please test Windows |
1 similar comment
|
Please test with following PRs: @swift-ci please test Windows |
Re-organise the "runtime" components (i.e. the Package Manifest runtime) into a separate directory. Introduce a separate CMake project for the build of this runtime to allow building the SPM tool with one version of the Swift runtime and the SPM Manifest Runtime witih a separate Swift runtime.